Codecov Report

Patch and project coverage have no change.

Comparison is base (58a395e) 89.95% compared to head (a7a5f2b) 89.95%.

@@           Coverage Diff           @@
##             main     #771   +/-   ##
=======================================
  Coverage   89.95%   89.95%           
=======================================
  Files          82       82           
  Lines       14708    14708           
=======================================
  Hits        13231    13231           
  Misses       1477     1477           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

If api33 weren't comptaible with java 17 bytecode how could #757 pass CI checks?

I'm not 100% sure how it worked. My assumption is that it's because the test app is also configured to compile with JDK 17. But importing it into Element Android (compileSdk 33 / JDK 11) reveals a problem:

bad class file: [..] jetified-wysiwyg-2.5.0-api.jar(/io/element/android/wysiwyg/[..].class)
    class file has wrong version 61.0 [Java 17], should be 55.0 [Java 11]

When I checked Java versions in Android builds docs, I saw the following compatibility table:

Use the table below to determine which Java version is supported by
each Android API, and where to find details on which Java APIs are available.

Android	Java
14 (API 34)	17
13 (API 33)	11

Oh I see, I think api33 works fine with java 17 bytecode, the problem is that EA is still built with v11 bytecode (so it can't use libraries built with v17). If we wish to keep compatibility with EA too then we have no choice but to lower ours bytecode version too.

Ok, I tried this but the build fails with an error:

> 'compileDebugJavaWithJavac' task (current target is 11) and 'compileDebugKotlin' task (current target is 17) jvm target compatibility should be set to the same Java version.

If I remove targetCompatibility JavaVersion.VERSION_11, then it builds but it's the same story as before - bytecode is not compatible with the EA build.

Ok, I tried this but the build fails with an error:

> 'compileDebugJavaWithJavac' task (current target is 11) and 'compileDebugKotlin' task (current target is 17) jvm target compatibility should be set to the same Java version.

If I remove targetCompatibility JavaVersion.VERSION_11, then it builds but it's the same story as before - bytecode is not compatible with the EA build.

Thanks for checking! We'll have to keep everything at 11 then as long as we want to maintain compatibility with legacy element.

Merging with test failures as these are unrelated and fixed in #772